SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Concurrent engineering</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Concurrent engineering</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1248332772">

/* start https://en.wikipedia.org/ */

.mw-parser-output .multiple-issues-text{width:95%;margin:0.2em 0}.mw-parser-output .multiple-issues-text>.mw-collapsible-content{margin-top:0.3em}.mw-parser-output .compact-ambox .ambox{border:none;border-collapse:collapse;background-color:transparent;margin:0 0 0 1.6em!important;padding:0!important;width:auto;display:block}body.mediawiki .mw-parser-output .compact-ambox .ambox.mbox-small-left{font-size:100%;width:auto;margin:0}.mw-parser-output .compact-ambox .ambox .mbox-text{padding:0!important;margin:0!important}.mw-parser-output .compact-ambox .ambox .mbox-text-span{display:list-item;line-height:1.5em;list-style-type:disc}body.skin-minerva .mw-parser-output .multiple-issues-text>.mw-collapsible-toggle,.mw-parser-output .compact-ambox .ambox .mbox-image,.mw-parser-output .compact-ambox .ambox .mbox-imageright,.mw-parser-output .compact-ambox .ambox .mbox-empty-cell,.mw-parser-output .compact-ambox .hide-when-compact{display:none}

/* end https://en.wikipedia.org/ */

</style>

<p><b>Concurrent engineering</b> (<b>CE</b>) or <b>concurrent design and manufacturing</b> is a work methodology emphasizing the parallelization of tasks (i.e. performing tasks concurrently), which is sometimes called <b>simultaneous engineering</b> or <b>integrated product development</b> (<b>IPD</b>) using an <a href="Integrated_product_team" title="Integrated product team">integrated product team</a> approach. It refers to an approach used in <a href="Product_development" class="mw-redirect" title="Product development">product development</a> in which functions of design engineering, manufacturing engineering, and other functions are integrated to reduce the time required to bring a new product to market.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p><p>

By completing the design and manufacturing stages at the same time, products are produced in less time while lowering cost. Although concurrent design and manufacturing requires extensive communication and coordination between disciplines, the benefits can increase the profit of a business and lead to a sustainable environment for product development. Concurrent design and manufacturing can lead to a competitive advantage over other businesses as the product may be produced and marketed in less time.<sup id="cite_ref-:0_2-0" class="reference"><a href="#cite_note-:0-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> However, poorly implemented concurrent engineering can lead to issues.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup></p>

<div class="mw-heading mw-heading2"><h2 id="Introduction">Introduction</h2></div>

<p>The success behind concurrent design and manufacturing lies within completing processes at the same time while involving all disciplines. As product development has become more cost and time efficient over the years, elements of concurrent engineering have been present in product development approaches. The elements of concurrent engineering that were utilized were cross-functional teams as well as fast time-to-market and considering manufacturing processes when designing.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> By involving multiple disciplines in decision making and planning, concurrent engineering has made product development more cost and time efficient. The fact that concurrent engineering could result in faster time-to-market is already an important advantage in terms of a competitive edge over other producers. Concurrent engineering has provided a structure and concept for product development that can be implemented for future success.

</p><p>A 2008 publication described concurrent engineering as a new design management system that has matured in recent years to become a well-defined systems approach to optimizing design and engineering cycles.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> Concurrent engineering has been implemented in a number of companies, organizations, and universities, most notably in the aerospace industry. Beginning in the early 1990s, CE was also adapted for use in the information and content automation field, providing a basis for organization and management of projects outside the physical product development sector for which it was originally designed. Organizations such as the <a href="ESA" class="mw-redirect" title="ESA">European Space Agency</a>'s <a href="Concurrent_Design_Facility" title="Concurrent Design Facility">Concurrent Design Facility</a> make use of concurrent design to perform feasibility studies for future missions.

</p><p>The basic premise for concurrent engineering revolves around two concepts. The first is the idea that all elements of a product's life-cycle—from functionality, production, assembly, testing, maintenance, environmental impact, and finally disposal and recycling—should be taken into careful consideration in the early design phases.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>

</p><p>The second concept is that design activities should all be occurring at the same time, i.e., concurrently. The idea is that the concurrent nature of these activities significantly increases productivity and product quality.<sup id="cite_ref-study_8-0" class="reference"><a href="#cite_note-study-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> This way, errors and redesigns can be discovered early in the design process when the project is still flexible. By locating and fixing these issues early, the design team can avoid what often become costly errors as the project moves to more complicated computational models and eventually into the actual manufacturing of hardware.<sup id="cite_ref-concurrent_9-0" class="reference"><a href="#cite_note-concurrent-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p><p>As mentioned above, part of the design process is to ensure that the product's entire life cycle is taken into consideration. This includes establishing user requirements, propagating early conceptual designs, running computational models, creating physical prototypes, and eventually manufacturing the product. Included in this process is taking into full account funding, workforce capability, and time requirements. A 2006 study claimed that a correct implementation of the concurrent design process can save a significant amount of money, and that organizations have been moving to concurrent design for this reason.<sup id="cite_ref-study_8-1" class="reference"><a href="#cite_note-study-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> It is also highly compatible with <a href="Systems_thinking" title="Systems thinking">systems thinking</a> and <a href="Green_engineering" title="Green engineering">green engineering</a>.

</p><p>Concurrent engineering replaces the more traditional sequential design flow, or "Waterfall Model".<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> In Concurrent Engineering an iterative or integrated development method is used instead.<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup> The Waterfall method moves in a linear fashion, starting with user requirements and sequentially moving forward to design and implementation, until you have a finished product. In this design system, a design team would not quickly look backward or forward from the step it is on to fix or anticipate problems. In the case that something does go wrong, the design usually must be scrapped or heavily altered. The concurrent or iterative design process encourages prompt changes of tack, so that all aspects of the life cycle of the product are taken into account, allowing for a more evolutionary approach to design.<sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> The difference between the two design processes can be seen graphically in Figure 1.

</p>

<p>A significant part of the concurrent design method is that the individual engineer is given much more say in the overall design process due to the collaborative nature of concurrent engineering. Giving the designer ownership is claimed to improve the productivity of the employee and quality of the product, based on the assumption that people who are given a sense of gratification and ownership over their work tend to work harder and design a more robust product, as opposed to an employee that is assigned a task with little say in the general process.<sup id="cite_ref-concurrent_9-1" class="reference"><a href="#cite_note-concurrent-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Challenges_associated_with_concurrent_design">Challenges associated with concurrent design</h3></div>

<p>Concurrent design comes with a series of challenges, such as implementation of early design reviews, dependency on efficient communication between engineers and teams, software compatibility, and opening up the design process.<sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup> This design process usually requires that computer models (<a href="Computer_aided_design" class="mw-redirect" title="Computer aided design">computer aided design</a>, <a href="Finite_element_analysis" class="mw-redirect" title="Finite element analysis">finite element analysis</a>) are exchanged efficiently, something that can be difficult in practice. If such issues are not addressed properly, concurrent design may not work effectively.<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup> It is important to note that although the nature of some project activities imposes a degree of linearity—completion of software code, prototype development and testing, for example—organizing and managing project teams to facilitate concurrent design can still yield significant benefits that come from the improved sharing of information.

</p><p>Service providers exist that specialize in this field, not only training people how to perform concurrent design effectively, but also providing the tools to enhance the communication between the team members.

</p>

<div class="mw-heading mw-heading2"><h2 id="Elements">Elements</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Cross-functional_teams">Cross-functional teams</h3></div>

<p>Cross-functional teams include people from different area of the workplace that are all involved in a particular process, including manufacturing, hardware and software design, marketing, and so forth.

</p>

<div class="mw-heading mw-heading3"><h3 id="Concurrent_product_realization">Concurrent product realization</h3></div>

<p>Doing several things at once, such as designing various subsystems simultaneously, is critical to reducing design time and is at the heart of concurrent engineering.

</p>

<div class="mw-heading mw-heading3"><h3 id="Incremental_information_sharing">Incremental information sharing</h3></div>

<p>Incremental information sharing helps minimize the chance that concurrent product realization will lead to surprises. "Incremental" meaning that as soon as new information becomes available, it is shared and integrated into the design. Cross-functional teams are important to the effective sharing of information in a timely fashion.

</p>

<div class="mw-heading mw-heading3"><h3 id="Integrated_project_management">Integrated project management</h3></div>

<p>Integrated project management ensures that someone is responsible for the entire project, and that responsibility is not handed-off once one aspect of the work is done.

</p>

<div class="mw-heading mw-heading2"><h2 id="Definition">Definition</h2></div>

<p>Several definitions of concurrent engineering are in use.

</p><p>The first one is used by the <a href="Concurrent_Design_Facility" title="Concurrent Design Facility">Concurrent Design Facility</a> (<a href="ESA" class="mw-redirect" title="ESA">ESA</a>):<br>

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .templatequote{overflow:hidden;margin:1em 0;padding:0 32px}.mw-parser-output .templatequotecite{line-height:1.5em;text-align:left;margin-top:0}@media(min-width:500px){.mw-parser-output .templatequotecite{padding-left:1.6em}}

/* end https://en.wikipedia.org/ */

</style><blockquote class="templatequote"><p>Concurrent Engineering (CE) is a systematic approach to integrated product development that emphasizes the response to customer expectations. It embodies team values of co-operation, trust and sharing in such a manner that decision making is by consensus, involving all perspectives in parallel, from the beginning of the <a href="Product_lifecycle_(engineering)" class="mw-redirect" title="Product lifecycle (engineering)">product life cycle</a>.</p></blockquote>

<p>The second one is by Winner, et al., 1988:<br>

</p>

<blockquote class="templatequote"><p>Concurrent Engineering is a systematic approach to the integrated, concurrent design of products and their related processes, including, manufacturing and support. This approach is intended to cause the developers from the very outset to consider all elements of the product life cycle, from conception to disposal, including quality, cost, schedule, and user requirements.<sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup></p></blockquote>

<div class="mw-heading mw-heading2"><h2 id="Concurrent_vs_sequential_engineering">Concurrent vs sequential engineering</h2></div>

<p>Concurrent and Sequential engineering cover the same stages of design and manufacturing, however, the two approaches vary widely in terms of productivity, cost, development and efficiency. The 'Sequential Engineering vs Concurrent Design and Manufacturing' figure shows sequential engineering on the left and concurrent design and manufacturing on the right. As seen in the figure, sequential engineering begins with customer requirements and then progresses to design, implementation, verification and maintenance. The approach for sequential engineering results in large amounts of time devoted to product development. Due to large amounts of time allocated towards all stages of product development, sequential engineering is associated with high cost and is less efficient as products can not be made quickly. Concurrent engineering, on the other hand, allows for all stages of product development to occur essentially at the same time. As seen in the 'Sequential Engineering vs Concurrent Design and Manufacturing' figure, initial planning is the only requirement before the process can occur including planning design, implementation, testing and evaluation. The concurrent design and manufacturing approach allows for shortening of product development time, higher efficiency in developing and producing parts earlier and lower production costs.

</p><p>Concurrent and Sequential Engineering may also be compared using a relay race analogy.<sup id="cite_ref-:1_17-0" class="reference"><a href="#cite_note-:1-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup> Sequential engineering is compared to the standard approach of running a relay race, where each runner must run a set distance and then pass the baton to the next runner and so on until the race is completed. Concurrent engineering is compared to running a relay race where two runners will run at the same time during certain points of the race. In the analogy, each runner will cover the same set distance as the sequential approach but the time to complete the race using the concurrent approach is significantly less. When thinking of the various runners in the relay race as stages in product development, the correlation between the two approaches in the relay race to the same approaches in engineering is vastly similar. Although there are more complex and numerous processes involved in product development, the concept that the analogy provides is enough to understand the benefits that come with concurrent design and manufacturing.

</p>

<div class="mw-heading mw-heading2"><h2 id="Business_benefits">Business benefits</h2></div>

<p>Using concurrent engineering, businesses can cut down on the time it takes to go from idea to product. The time savings come from designing with all the steps of the process in mind, eliminating any potential changes that have to be made to a design after a part has gone all the way to production before realizing that it is difficult or impossible to machine. Reducing or eliminating these extra steps means the product will be completed sooner and with less wasted material in the process. During the design and prototyping process, potential issues in the design can be corrected earlier in the product development stages to further reduce the production time frame.

</p><p>The benefits of concurrent design and manufacturing can be sorted in to short term and long term.

</p>

<div class="mw-heading mw-heading3"><h3 id="Short_term_benefits">Short term benefits</h3></div>

<ul><li>Competitive advantage with implementing part into market quickly</li>

<li>Large amounts of same part produced in a shorter amount of time</li>

<li>Allows for early correction of part</li>

<li>Less material wasted</li>

<li>Less time spent on multiple iterations of essentially the same part</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Long_term_benefits">Long term benefits</h3></div>

<ul><li>More cost efficient over several parts produced and several years</li>

<li>Large amounts of different parts produced in a shorter total amount of time</li>

<li>Better communication between disciplines in company</li>

<li>Ability to leverage teamwork and make informed decisions<sup id="cite_ref-:1_17-1" class="reference"><a href="#cite_note-:1-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Using_C.E.">Using C.E.</h2></div>

<p>Currently, several companies, agencies and universities use CE. Among them can be mentioned:

</p>

<ul><li><a href="Concurrent_Design_Facility" title="Concurrent Design Facility">Concurrent Design Facility</a><sup id="cite_ref-18" class="reference"><a href="#cite_note-18"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup> - <a href="European_Space_Agency" title="European Space Agency">European Space Agency</a></li>

<li><a href="NASA" title="NASA">NASA</a> <a rel="nofollow" class="external text" href="https://jplteamx.jpl.nasa.gov/">Team X</a> - Jet Propulsion Laboratory</li>

<li><a href="NASA" title="NASA">NASA</a> <a rel="nofollow" class="external text" href="https://idc.nasa.gov">Integrated Design Center (IDC), Mission Design Lab (MDL), and Instrument Design Lab (IDL)</a> - Goddard Space Flight Center</li>

<li><a href="Compass_(NASA)" title="Compass (NASA)">NASA Compass Team</a><sup id="cite_ref-19" class="reference"><a href="#cite_note-19"><span class="cite-bracket">[</span>19<span class="cite-bracket">]</span></a></sup> - Glenn Research Center</li>

<li><a href="CNES" title="CNES">CNES</a><sup id="cite_ref-20" class="reference"><a href="#cite_note-20"><span class="cite-bracket">[</span>20<span class="cite-bracket">]</span></a></sup> – French Space Agency</li>

<li><a href="Italian_Space_Agency" title="Italian Space Agency">ASI</a> – Italian Space Agency</li>

<li><a href="Boeing" title="Boeing">Boeing</a></li>

<li><a href="EADS_Astrium" class="mw-redirect" title="EADS Astrium">EADS Astrium</a> – Satellite Design Office</li>

<li><a href="Thales_Alenia_Space" title="Thales Alenia Space">Thales Alenia Space</a></li>

<li><a href="The_Aerospace_Corporation" title="The Aerospace Corporation">The Aerospace Corporation</a> Concept Design Center</li>

<li><a href="STV_Group_(United_States)" class="mw-redirect" title="STV Group (United States)">STV Incorporated</a></li>

<li><a href="German_Aerospace_Center" title="German Aerospace Center">German Aerospace Center</a> <a rel="nofollow" class="external text" href="https://www.dlr.de/irs/en/desktopdefault.aspx/tabid-11079/#gallery/29532">Concurrent Engineering Facility</a></li>

<li><a rel="nofollow" class="external text" href="http://space.epfl.ch/page-39445-en.html">EPFL Space Center</a></li>

<li><a href="Schlumberger" title="Schlumberger">Schlumberger</a></li>

<li><a href="Harley_Davidson" class="mw-redirect" title="Harley Davidson">Harley Davidson</a></li>

<li>Fiberthree</li>

<li><a href="Toyota" title="Toyota">Toyota</a></li></ul>

<ul><li><a href="ESA" class="mw-redirect" title="ESA">ESA</a>'s <a href="Concurrent_Design_Facility" title="Concurrent Design Facility">Concurrent Design Facility</a></li>

<li><a href="Iterative_design" title="Iterative design">Iterative design</a></li>

<li><a href="New_product_development" title="New product development">New product development</a></li>

<li><a href="Open_Concurrent_Design_Server" title="Open Concurrent Design Server">Open Concurrent Design Server</a></li>

<li><a href="Product_lifecycle_(engineering)" class="mw-redirect" title="Product lifecycle (engineering)">Product Life Cycle</a></li>

<li><a href="Product_lifecycle_management" class="mw-redirect" title="Product lifecycle management">Product lifecycle management</a></li>

<li><a href="Traditional_engineering" title="Traditional engineering">Traditional engineering</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.npd-solutions.com/principles.html">"The Principles of Integrated Product Development"</a>. <i>NPD Solutions</i>. DRM Associates. 2016<span class="reference-accessdate">. Retrieved <span class="nowrap">7 May</span> 2017</span>.</cite></span>

</li>

<li id="cite_note-:0-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-:0_2-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFPartner" class="citation web cs1">Partner, Concurrent Engineering | PTC. <a rel="nofollow" class="external text" href="http://www.concurrent-engineering.co.uk/what-is-concurrent-engineering">"What is Concurrent Engineering?"</a>. <i>www.concurrent-engineering.co.uk</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2016-02-16</span></span>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite id="CITEREFOkpalaDara2017" class="citation web cs1">Okpala, Charles Chikwendu; Dara, Jude E. (August 2017). <a rel="nofollow" class="external text" href="https://www.jmest.org/wp-content/uploads/JMESTN42352333.pdf">"Benefits and Barriers to Successful Concurrent Engineering Implementation"</a> <span class="cs1-format">(PDF)</span>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite id="CITEREFMathiasenMathiasen2016" class="citation web cs1">Mathiasen, John Bang; Mathiasen, Rasmus Munksgard (September 23–25, 2016). <a rel="nofollow" class="external text" href="http://ieomsociety.org/ieomdetroit/pdfs/230.pdf">"Concurrent engineering: The drawbacks of applying a one-size-fits-all approach"</a> <span class="cs1-format">(PDF)</span>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite id="CITEREFLoch,_Terwiesch1998" class="citation journal cs1">Loch, Terwiesch (1998). <a rel="nofollow" class="external text" href="https://www.insead.edu/facultyresearch/research/doc.cfm?did=46444">"Product Development and Concurrent Engineering"</a>. <i>INSEAD</i><span class="reference-accessdate">. Retrieved <span class="nowrap">March 8,</span> 2016</span>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text">Ma, Y., Chen, G. & Thimm, G.; "Paradigm Shift: Unified and Associative Feature-based Concurrent Engineering and Collaborative Engineering", <i>Journal of Intelligent Manufacturing</i>, <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2Fs10845-008-0128-y">10.1007/s10845-008-0128-y</a></span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text">Kusiak, Andrew; <i>Concurrent Engineering: Automation, Tools and Techniques</i></span>

</li>

<li id="cite_note-study-8"><span class="mw-cite-backlink">^ <a href="#cite_ref-study_8-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-study_8-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Quan, W. & Jianmin, H., <i><a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/abstract/document/4127103/">A Study on Collaborative Mechanism for Product Design in Distributed Concurrent Engineering</a></i> IEEE 2006. DOI: 10.1109/CAIDCD.2006.329445</span>

</li>

<li id="cite_note-concurrent-9"><span class="mw-cite-backlink">^ <a href="#cite_ref-concurrent_9-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-concurrent_9-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Kusiak, Andrew, <i>Concurrent Engineering: Automation, Tools and Techniques</i></span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text">"The standard waterfall model for systems development", <a rel="nofollow" class="external text" href="https://web.archive.org/web/20050310133243/http://asd-www.larc.nasa.gov/barkstrom/public/The_Standard_Waterfall_Model_For_Systems_Development.htm">NASA Webpage</a>, November 14, 2008</span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text">Kock, N. and Nosek, J., "<a rel="nofollow" class="external text" href="https://www.researchgate.net/profile/Ned_Kock/publication/3230350_Expanding_the_Boundaries_of_E-Collaboration/links/0f317538725c67ae7b000000/Expanding-the-Boundaries-of-E-Collaboration.pdf">Expanding the Boundaries of E-Collaboration</a>", <i>IEEE Transactions on Professional Communication</i>, Vol 48 No 1, March 2005.</span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text">Ma, Y., Chen, G., Thimm, G., "Paradigm Shift: Unified and Associative Feature-based Concurrent Engineering and Collaborative Engineering", <i>Journal of Intelligent Manufacturing</i>, <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2Fs10845-008-0128-y">10.1007/s10845-008-0128-y</a></span>

</li>

<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13">^</a></b></span> <span class="reference-text">Royce, Winston, "<a rel="nofollow" class="external text" href="https://leadinganswers.typepad.com/leading_answers/files/original_waterfall_paper_winston_royce.pdf">Managing the Development of Large Software Systems</a>", <i>Proceedings of IEEE WESCON</i> 26 (August 1970): 1-9.</span>

</li>

<li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14">^</a></b></span> <span class="reference-text">Kusiak, Andrew, "Concurrent Engineering: Automation, Tools and Techniques"</span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text">Rosenblatt, A. and Watson, G. (1991). "Concurrent Engineering", <i>IEEE Spectrum</i>, July, pp 22-37.</span>

</li>

<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text">Winner, Robert I., Pennell, James P., Bertrand, Harold E., and Slusarczuk, Marko M. G. (1991). "<a rel="nofollow" class="external text" href="https://apps.dtic.mil/dtic/tr/fulltext/u2/a203615.pdf">The Role of Concurrent Engineering in Weapons System Acquisition</a>", <i>Institute for Defense Analyses Report R-338</i>, December 1988, p v.</span>

</li>

<li id="cite_note-:1-17"><span class="mw-cite-backlink">^ <a href="#cite_ref-:1_17-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:1_17-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFPrasad1995" class="citation journal cs1">Prasad, Biren (1995). <a rel="nofollow" class="external text" href="https://www.researchgate.net/publication/238837262">"Sequential versus Concurrent Engineering—An Analogy"</a>. <i>Concurrent Engineering</i>. <b>3</b> (4): <span class="nowrap">250–</span>255. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1177%2F1063293X9500300401">10.1177/1063293X9500300401</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:110354984">110354984</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2016-03-04</span></span>.</cite></span>

</li>

<li id="cite_note-18"><span class="mw-cite-backlink"><b><a href="#cite_ref-18">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.esa.int/Enabling_Support/Space_Engineering_Technology/Concurrent_Design_Facility">"Concurrent Design Facility"</a>. <i>www.esa.int</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2021-11-30</span></span>.</cite></span>

</li>

<li id="cite_note-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-19">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www1.grc.nasa.gov/facilities/compass-lab/">"Compass Lab"</a>. <i>Glenn Research Center | NASA</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2021-10-07</span></span>.</cite></span>

</li>

<li id="cite_note-20"><span class="mw-cite-backlink"><b><a href="#cite_ref-20">^</a></b></span> <span class="reference-text"><cite id="CITEREFBousquetBenoistGonzalezGillen2005" class="citation cs2">Bousquet, P. W.; Benoist, J.; Gonzalez, Fr; Gillen, Ph; Pillet, N.; Sire, J.-P.; Vigeant, F. (2005), <span class="id-lock-subscription" title="Paid subscription required"><a rel="nofollow" class="external text" href="https://arc.aiaa.org/doi/abs/10.2514/6.IAC-05-D1.3.06">"Concurrent Engineering at CNES"</a></span>, <i>56th International Astronautical Congress of the International Astronautical Federation, the International Academy of Astronautics, and the International Institute of Space Law</i>, American Institute of Aeronautics and Astronautics, <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.2514%2F6.iac-05-d1.3.06">10.2514/6.iac-05-d1.3.06</a><span class="reference-accessdate">, retrieved <span class="nowrap">2021-11-30</span></span></cite></span>

</li>

</ol></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-05-25" href="https://en.wikipedia.org/wiki/?title=Concurrent_engineering&oldid=1292233849">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>